I think it should be possible to use Postgres string functions to format this instead of directly transposing it.

Have a look at initcap() and replace() here - https://www.postgresql.org/docs/current/functions-string.html

Happy to talk this through if easier - just let me know 👍

So instead of the name = slug, I would de-slugify the slug and add it to the name?

Ah I figured initcap() would just handle the first letter, not the first letter of each word. This makes it trickier for sure!

Using "xax" is clever and certainly works as we don't have this substring in any flow slugs (tested with select * from flows where slug ilike '%xax%';

However it's a little bit unintuitive and took me a while to work out what was going on here 😅 It also relies on strings which users could modify.

Is there another approach here that might be more robust? It should be possible to use substrings (e.g. upper case just first letter, concatenate with remaining lowercase string).

https://pgplayground.com/ can be handy as a quick playground for functions like this 👍

Aha, so I should be explicitly altering the first letter as it'll always output the same result no matter what the user adds (unless they use dashes), and it's clearer to read?

Something like this:

SET name = replace(concat(upper(substring(slug,1,1)),right(slug,-1)),'-',' ')

And using the above UPPER method is easier to read than my previous method, so even changing out the xax string to use something like _ wouldn't make it more robust, as shown below.

SET name = replace(initcap(replace(slug,'-','_')),'_',' ')

I've been using the Hasura SQL console to try different methods since it required less setup... any concerns with that?

No - totally legit and safe to use your local Hasura console for this also! 👌

I'd favour the first option as despite being fairly complex syntax, the intention feels pretty clear.

However, the second approach would also work well and I have no objections! 👍

As seen below, users cannot have special characters in the existing slug, so using the special character _ as a replacement string is safe -

And however unlikely it is that they use the string xax, it's certainly possible, so it's best not to use this -